-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XML tag using def #921
XML tag using def #921
Conversation
LGTM 🚀 The changes in this pull request look good to me. The addition of the Overall, these changes improve the flexibility and functionality of the template system without introducing any obvious functional issues.
|
Investigator report(view differences in changes made between the latest successful commit and the run that failed)
|
Based on the provided workflow configuration, the job 'build' is triggered by several events and includes a matrix strategy for different Node.js versions. The steps in the job involve checking out code, setting up Node.js, running Yarn install, type checking, compiling, linting, packaging VSCode, compiling system scripts, and running unit tests. To identify the root cause of failure for job 'build (20)', we need the SHA or head_sha value from the most recent successful run for that job. Please provide this information so I can assist you further.
|
{
"response": "<error>Tool not found</error>"
}
|
LLMs have been trained to support xml tags. This changes adds support for those.
Removed redundant model specifications across various scripts (UI to change token #23)
vision
model referenceConsolidated duplicate logic for processing images (prompt should be opened in 50% to enable dev flow #24)
defImages
)Updated default behavior of scripts to check if file array is empty before proceeding with execution